Method and device having touchscreen keyboard with visual cues

ABSTRACT

A method for providing visual cues rendered on a display is provided. The method comprises: detecting a touch input associated with a user interface element rendered on the display; determining an input direction of the touch input; and displaying on the display a visual cue associated with the user interface element, wherein the visual cue is located at a position based on the input direction of the touch input.

RELATED APPLICATION DATA

The present disclosure relates to commonly owned U.S. patent applicationSer. No. 13/373,356, filed Nov. 10, 2011, which is incorporated hereinby reference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to input methodologies forelectronic devices, such as handheld electronic devices, and moreparticularly, to a method and device for touchscreen keyboard withvisual cues.

BACKGROUND

Increasingly, electronic devices, such as computers, netbooks, cellularphones, smart phones, personal digital assistants, tablets, etc., havetouchscreens that allow a user to input characters into an application,such as a word processor or email application. Character input ontouchscreens can be a cumbersome task due to, for example, the smalltouchscreen area, particularly where a user needs to input a longmessage.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example block diagram of an electronic device, consistentwith embodiments disclosed herein.

FIG. 2 is a flowchart illustrating an example method for predicting aselected set of characters, consistent with embodiments disclosedherein.

FIGS. 3A, 3B, 3C, and 3D show example front views of a touchscreen,consistent with embodiments disclosed herein.

FIGS. 4A and 4B show example front views of a touchscreen, consistentwith embodiments disclosed herein.

FIG. 5 shows an example front view of a touchscreen, consistent withembodiments disclosed herein.

FIGS. 6A, 6B, and 6C show example front views of a touchscreen,consistent with embodiments disclosed herein.

FIG. 7 shows an example front view of a touchscreen, consistent withembodiments disclosed herein.

FIGS. 8A and 8B show example front views of a touchscreen, consistentwith embodiments disclosed herein.

FIG. 9 shows an example front view of a touchscreen, consistent withembodiments disclosed herein.

FIGS. 10A and 10B show example front views of a touchscreen, consistentwith embodiments disclosed herein.

FIGS. 11A and 11B show example front views of a touchscreen, consistentwith embodiments disclosed herein.

FIGS. 12A and 12B show example front views of a touchscreen, consistentwith embodiments disclosed herein.

FIGS. 13A and 13B show example front views of a touchscreen, consistentwith embodiments disclosed herein.

FIGS. 14A, 14B, and 14C show example front views of a touchscreen,consistent with embodiments disclosed herein.

FIG. 15 shows an example front view of a touchscreen, consistent withembodiments disclosed herein.

FIG. 16 shows an example front view of a touchscreen, consistent withembodiments disclosed herein.

FIG. 17 is a flowchart illustrating an example method, consistent withembodiments disclosed herein.

FIG. 18 is a flowchart illustrating an example method, consistent withembodiments disclosed herein.

FIG. 19 is a flowchart illustrating an example method, consistent withembodiments disclosed herein.

FIG. 20 shows an example front view of a virtual keyboard for display ona touchscreen, consistent with embodiments disclosed herein.

FIG. 21 shows an example front view of a virtual keyboard for display ona touchscreen, consistent with embodiments disclosed herein.

FIG. 22 is a flowchart illustrating an example method, consistent withembodiments disclosed herein.

FIGS. 23 to 24 show example front views of a virtual keyboard fordisplay on a touchscreen, consistent with embodiments disclosed herein.

FIG. 25 illustrates a Cartesian dimensional coordinate system suitablefor mapping locations of the touchscreen and determining a shape of thecontact area of the user's finger in accordance with one embodiment ofthe present disclosure.

FIGS. 26 to 28 show example front views of a virtual keyboard fordisplay on a touchscreen, consistent with embodiments disclosed herein.

FIG. 29 is a flowchart illustrating an example method, consistent withembodiments disclosed herein.

FIG. 30 shows an example front view of a virtual keyboard for display ona touchscreen, consistent with embodiments disclosed herein.

FIG. 31 is a flowchart illustrating an example method, consistent withembodiments disclosed herein.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Reference will now be made in detail to various embodiments, examples ofwhich are illustrated in the accompanying drawings. Wherever possible,the same reference numbers will be used throughout the drawings to referto the same or like parts.

The present disclosure relates to an electronic device, including wiredcommunication devices (for example, a laptop computer having atouchscreen) and mobile or handheld wireless communication devices suchas cellular phones, smartphones, wireless organizers, personal digitalassistants, wirelessly enabled notebook computers, tablets, and similardevices. The electronic device can also be an electronic device withoutwireless communication capabilities, such as a handheld electronic gamedevice, digital photograph album, digital camera, or other device.

Basic predictive text input solutions have been introduced for assistingwith input on an electronic device. These solutions include predictingwhich word a user is entering and offering a suggestion for completingthe word. But these solutions can have limitations, often requiring theuser to input most or all of the characters in a word before thesolution suggests the word the user is trying to input. Even then, auser often has to divert focus from the keyboard to view and considerthe suggested word displayed elsewhere on the display of the electronicdevice, and thereafter, look back at the keyboard to continue typing.Refocusing of one's eyes relative to the keyboard while inputtinginformation in an electronic device, particularly when composing largetexts, can strain the eyes and be cumbersome, distracting, and otherwiseinefficient. Moreover, processing cycles are lost and display powerwasted as the processor is idling while the user is focusing attentionto the input area, and then back at the virtual keyboard.

The efficiency of predictive text input solutions, from the perspectiveof both device resources and user experience, sometimes depends on theparticular user and the nature of the interaction of the particular userwith the touchscreen. Virtual keyboard usage patterns can be broadlycategorized as being of two types: “rapid” and “precise”. Rapid typistsare typically fast two-thumb typists which rely on auto-correction. Thisusage pattern corresponds most closely with experienced, frequenttouchscreen users. Precise typists are typically careful typists who areinclined to use a single finger point to tap keys in the virtualkeyboard, and often choose predictions as an input accelerator ratherthan auto-correction. This usage pattern corresponds most closely withnovice/new touchscreen users as well as potentially one-handed (thumb)use situations.

Accordingly, example embodiments described herein permit the user of anelectronic device to input characters without diverting attention fromthe keyboard and subsequently refocusing. Example embodiments describedherein also seek to accommodate different user types, such as rapidtypists and precise typists, and the different efficiency challengespresented by the different user types.

Use of the indefinite article “a” or “an” in the specification and theclaims is meant to include one or more than one of the feature that itintroduces, unless otherwise indicated. Thus, the term “a set ofcharacters” as used in “generating a set of characters” can include thegeneration of one or more than one set of characters. Similarly, use ofthe definite article “the”, or “said,” particularly after a feature hasbeen introduced with the indefinite article, is meant to include one ormore than one of the feature to which it refers (unless otherwiseindicated). Therefore, the term “the generated set of characters” asused in “displaying the generated set of characters” includes displayingone or more generated set of characters. References to orientationcontained herein, such as horizontal and vertical, are relative to thescreen orientation of a graphical user interface rather than anyphysical orientation.

In accordance with one embodiment, there is provided a method comprisingreceiving an input of a character from a virtual keyboard rendered on adisplay; generating one or more sets of predicted input characters basedon the input character; and displaying one or more of the generated setsof predicted input characters.

In accordance with one embodiment, there is provided a method forproviding a virtual keyboard rendered on a display with visual cues,comprising: detecting a touch input associated with a user interfaceelement rendered on the display; determining an input direction of thetouch input; and displaying on the display a visual cue associated withthe user interface element, wherein the visual cue is located at aposition based on the input direction of the touch input.

In accordance with a further embodiment, there is provided a method forproviding visual cues rendered on a display, comprising: detecting atouch input associated with a user interface element rendered on thedisplay; determining whether the touch input is associated with a lefthand or a right hand of a user; and displaying on the display a visualcue associated with the user interface element, wherein the visual cueis located at a position based on whether the touch input is associatedwith the left hand or the right hand.

In a further embodiment, an electronic device is provided that comprisesa display having a virtual keyboard rendered thereupon, and a processor.The processor can be configured to perform methods described herein.

In a further embodiment, a keyboard rendered on a display of anelectronic device is provided. The keyboard can include a plurality ofkeys, each key corresponding to one or more different characters of aplurality of characters. The keyboard is configured to perform methodsdescribed herein in response to receiving an input.

In a further embodiment, a non-transitory computer-readable storagemedium is provided that includes computer executable instructions forperforming methods described herein.

These example embodiments, as well as those described below, permit theuser of an electronic device to input a set of characters withoutdiverting attention from the virtual keyboard and subsequentlyrefocusing. Predicting and providing various options that the user islikely contemplating, and doing so at appropriate locations on thekeyboard, allows the focus to remain on the keyboard, which enhancesefficiency, accuracy, and speed of character input.

FIG. 1 is a block diagram of an electronic device 100, consistent withexample embodiments disclosed herein. Electronic device 100 includesmultiple components, such as a main processor 102 that controls theoverall operation of electronic device 100. Communication functions,including data and voice communications, are performed through acommunication subsystem 104. Data received by electronic device 100 isdecompressed and decrypted by a decoder 106. The communication subsystem104 receives messages from and sends messages to a network 150. Network150 can be any type of network, including, but not limited to, a wirednetwork, a data wireless network, voice wireless network, and dual-modewireless networks that support both voice and data communications overthe same physical base stations. Electronic device 100 can be abattery-powered device and include a battery interface 142 for receivingone or more batteries 144.

Main processor 102 is coupled to and can interact with additionalsubsystems such as a Random Access Memory (RAM) 108; a memory 110, suchas a hard drive, CD, DVD, flash memory, or a similar storage device; oneor more actuators 120; one or more force sensors 122; an auxiliaryinput/output (I/O) subsystem 124; a data port 126; a speaker 128; amicrophone 130; short-range communications 132; other device subsystems134; and a touchscreen 118.

Touchscreen 118 includes a display 112 with a touch-active overlay 114connected to a controller 116. User-interaction with a graphical userinterface (GUI), such as a virtual keyboard rendered on the display 112as a GUI for input of characters, or a web-browser, is performed throughtouch-active overlay 114. Main processor 102 interacts with touch-activeoverlay 114 via controller 116. Characters, such as text, symbols,images, and other items are displayed on display 112 of touchscreen 118via main processor 102. Characters are inputted when the user touchesthe touchscreen at a location associated with said character.

Touchscreen 118 is connected to and controlled by main processor 102.Accordingly, detection of a touch event and/or determining the locationof the touch event can be performed by main processor 102 of electronicdevice 100. A touch event includes in some embodiments, atop by afinger, a swipe by a finger, a swipe by a stylus, along press by fingeror stylus, or a press by a finger for a predetermined period of time,and the like.

While specific embodiments of a touchscreen have been described, anysuitable type of touchscreen for an electronic device can be used,including, but not limited to, a capacitive touchscreen, a resistivetouchscreen, a surface acoustic wave (SAW) touchscreen, an embeddedphoto cell touchscreen, an infrared (IR) touchscreen, a straingauge-based touchscreen, an optical imaging touchscreen, a dispersivesignal technology touchscreen, an acoustic pulse recognition touchscreenor a frustrated total internal reflection touchscreen. The type oftouchscreen technology used in any given embodiment will depend on theelectronic device and its particular application and demands.

Main processor 102 can also interact with a positioning system 136 fordetermining the location of electronic device 100. The location can bedetermined in any number of ways, such as by a computer, by a GlobalPositioning System (GPS), either included or not included in electricdevice 100, through a Wi-Fi network, or by having a location enteredmanually. The location can also be determined based on calendar entries.

Main processor 102 can also interact with an orientation sensor 197 forsensing the orientation of the device. In some examples, the orientationsensor 197 may be one or more accelerometers. In some examples, theorientation sensor may detect acceleration along multiple orthogonalaxes. Main processor 102 can also interact with one or more proximitysensors 198 for detecting the proximity of nearby objects. In someexamples, the proximity sensor may be one or more infraredemitter/sensor pairs. The main processor 102 can also interact with anambient light sensor 199 for detecting the intensity and/or colortemperature of ambient light.

In some embodiments, to identify a subscriber for network access,electronic device 100 uses a Subscriber Identity Module or a RemovableUser Identity Module (SIM/RUIM) card 138 inserted into a SIM/RUIMinterface 140 for communication with a network, such as network 150.Alternatively, user identification information can be programmed intomemory 110.

Electronic device 100 also includes an operating system 146 and programs148 that are executed by main processor 102 and are typically stored inmemory 110. Additional applications may be loaded onto electronic device100 through network 150, auxiliary I/O subsystem 124, data port 126,short-range communications subsystem 132, or any other suitablesubsystem.

A received signal such as a text message, an e-mail message, or web pagedownload is processed by communication subsystem 104 and this processedinformation is then provided to main processor 102. Main processor 102processes the received signal for output to display 112, to auxiliaryI/O subsystem 124, or a combination of both. A user can compose dataitems, for example e-mail messages, which can be transmitted overnetwork 150 through communication subsystem 104. For voicecommunications, the overall operation of electronic device 100 issimilar. Speaker 128 outputs audible information converted fromelectrical signals, and microphone 130 converts audible information intoelectrical signals for processing.

FIG. 2 is a flowchart illustrating an example method 200 for predictinga set of characters, consistent with example embodiments disclosedherein. As used herein, a predictor (such as a predictive algorithm,program or firmware) includes a set of instructions that when executedby a processor (for example, main processor 102), can be used todisambiguate for example, received ambiguous text input and providevarious options, such as a set of characters (for example, words orphrases, acronyms, names, slang, colloquialisms, abbreviations, or anycombination thereof) that a user might be contemplating. A predictor canalso receive otherwise unambiguous text input and predict a set ofcharacters potentially contemplated by the user based on severalfactors, such as context, frequency of use, and others as appreciated bythose skilled in the field.

For example, in the predictor is a program 148 residing in memory 110 ofelectronic device 100. Accordingly, method 200 includes a predictor forgenerating a set of characters corresponding to a subsequent candidateinput character based on inputted characters. It can be appreciated thatwhile the example embodiments described herein are directed to apredictor program executed by a processor, the predictor can be executedby a virtual keyboard controller.

Method 200 begins at block 210, where the processor receives an input ofone or more characters from a virtual keyboard displayed on atouchscreen. As used herein, however, a character can be anyalphanumeric character, such as a letter, a number, a symbol, apunctuation mark, and the like. The inputted character can be displayedin an input field (for example, input field 330 further described belowin FIGS. 3-9) that displays the character the user inputs using thevirtual keyboard.

At block 220, the processor generates one or more sets of characterssuch as words or phrases, acronyms, names, slang, colloquialisms,abbreviations, or any combination thereof based on the input received inblock 210. The set of characters includes, for example, a set ofcharacters that are stored in a dictionary (for example, a word or anacronym) of a memory of the electronic device, a set of characters thatwere previously inputted by user (for example, a name or acronym), a setof characters based on a hierarchy or tree structure, a combinationthereof, or any set of characters that are selected by a processor basedon defined arrangement.

In some embodiments, the processor can use contextual data forgenerating a set of characters. Contextual data considers the context ofcharacters in the input field. Contextual data can include informationabout, for example, set of characters previously inputted by the user,grammatical attributes of the characters inputted in the input field(for example, whether a noun or a verb is needed as the next set ofcharacters in a sentence), or any combination thereof. For example, ifthe set of characters “the” has already been inputted into display, theprocessor can use the contextual data to determine that a noun—insteadof a verb will be the next set of characters after “the”. Likewise, ifthe set of characters “Guy Lafleur played in the National Hockey” wasinputted, based on the context, the processor can determine thesubsequent set of characters is likely “League”. Using the contextualdata, the processor can also determine whether an inputted character wasincorrect. For example, the processor can determine that the inputtedcharacter was supposed to be a “w” instead of an “a”, given theproximity of these characters on a QWERTY virtual keyboard.

Processor 102 can also include an affix as part of the set ofcharacters, such as an adverb ending, an adjective ending, differentverb tenses, and the like, or any other change to make a complete set ofcharacters. Processor 102 can also use the received input to generateaffixes, such as plural endings or plural forms. Any known predictivetechnique or software can be used to process the received input and thecontextual data in generating set of characters at block 220.

In some example embodiments, the set of characters generated at block220 can begin with the same character received as input at block 210.For example, if the characters “pl” have been received as input using avirtual keyboard, these characters will be received by the processor asthe input. In these embodiments, the set of characters generated atblock 220 would all begin with “pl”, such as “please” or “plot.” Thereis no limit on the length of a generated set of characters. Regardingaffixes, if the user has input the characters “child”, for example, theaffixes generated at block 220 could include “-ren”, to make the set ofcharacters “children”, or “-ish”, to make the set of characters“childish”.

In some example embodiments, the set of characters generated at block220 can simply include the same characters received as input at block210. For example, if the received input is an “x,” the processor maygenerate “example” or “xylophone” as the set of characters. Such sets ofcharacters can be generated using the contextual data.

In another example embodiment, if input has not been received or adelimiter (such as a <SPACE>) has been used, the generated set ofcharacters can be placed on subsequent candidate input characters thatcorrespond to the first letter of the generated set of characters.

Next, at block 230, the generated set of characters from block 220 canbe ranked. The rankings reflect the likelihood that a candidate set ofcharacters might have been intended by the user, or might be chosen by auser compared to another candidate set of characters.

In some embodiments, contextual data can be included in the ranking atblock 230. In some embodiments, the electronic device can be configuredto rank nouns or adjectives higher based on the previous inputted set ofcharacters. If the inputted set of characters is suggestive of a noun oradjective, the processor, using the contextual data, can rank the nounsor adjectives corresponding to what the user is typing higher at block230. In an additional embodiment, set of characters including adjectiveaffixes (such as “-ish” or “-ful”) phrases, plurals, or combinationsthereof can also be ranked. Contextual data can increase the likelihoodthat the higher ranked generated set of characters are intended by auser. In some embodiments, contextual data can include information aboutwhich programs or applications are currently running or being used by auser. For example, if the user is running an email application, then setof characters associated with that user's email system, such as set ofcharacters from the user's contact list, can be used to determine theranking. N-grams, including unigrams, bigrams, trigrams, and the like,can be also used in the ranking of the sets of characters.Alternatively, the geolocation of the electronic device or user can beused in the ranking process. If, for example, the electronic devicerecognizes that a user is located at his/her office, then sets ofcharacters generally associated with work can be ranked higher in thelist. If, on the other hand, the device determines a user is at thebeach, then sets of characters generally associated with the beach canbe ranked higher in the list.

At block 240, the processor determines which of the set of characters todisplay based on the ranking. For example, higher ranked sets ofcharacters are more likely to be determined that they should bedisplayed. A ranker (such as a ranking algorithm, program or firmware)includes a set of instructions that when executed by a processor (forexample, main processor 102), can be executed to determine ranking inthis regard. In some embodiments, the ranker is a program 146 residingin memory 110 of electronic device 100.

At block 250, the determined set of characters is displayed at alocation on the keyboard corresponding to a subsequent candidate inputcharacter, predicted as the next character in a word that the user mightinput. For instance, if a user inputs “pl”, the word “please” would bedisplayed on the key for the letter “e”—the subsequent candidate inputcharacter for that word. Similarly, the word “plus” would also bedisplayed on the key for the letter “u”—another subsequent candidateinput character. The subsequent candidate input character can be anyalphanumeric character, such as a letter, number, symbol, punctuationmark, and the like.

In some embodiments, the generated set of characters is displayed at ornear keys on the virtual keyboard associated with the subsequentcandidate input characters. Its placement at or near a key can depend,for instance, on the size of the word or the number of nearby subsequentcandidate input characters and the size of their associated set ofcharacters.

The set of characters can be displayed in a manner that will attract theuser's attention. In some embodiments, a displayed set of character'sappearance can be enhanced or changed in a way that makes the set morereadily visible to the user. For example, displayed sets of characterscan be displayed with backlighting, highlighting, underlining, bolding,italicizing, using combinations thereof, or in any other way for makingthe displayed set of characters more visible.

When identifying the set of characters for display at block 240, theprocessor can limit the displayed set of characters to the top few orchoose among the higher ranked sets of characters. For example, if twosets of characters are both ranked high, and these sets of characterswould otherwise be displayed at the same key, the electronic devicecould be configured to display only the highest ranked generated set ofcharacters. In other embodiments, both sets of characters could bedisplayed at or around the same key, or one set of characters isdisplayed at one key while the second set of characters is displayed atanother key. In some example embodiments, the processor can take intoaccount the display size to limit the number of generated sets ofcharacters.

In some embodiments, the ranking could be used to choose between two ormore sets of characters that, when displayed on adjacent subsequentcandidate input characters, would overlap with each other (e.g., becauseof their respective lengths). In such a scenario, the electronic devicecould be configured to display the higher ranked set of characters onthe keyboard. For example, if the set of characters “establishment” isranked first in a list generated at block 240 after the letter “E” isinputted, “establishment” could be displayed at the “S” key. Whendisplayed on a virtual keyboard, however, its length might occupy somespace on the “A” key and the “D” key, potentially blocking a set ofcharacters that would be displayed on or around those keys. At block240, it could be determined that “establishment” would be displayedfully, and no other set of characters would be placed at the “A” or “D”keys ahead of the first ranked set of characters “establishment.” Analternative to displaying only the top ranked set of characters would beto use abbreviations or recognized shortened forms of the set ofcharacters, effectively permitting a long set of characters to bedisplayed within or mostly within the boundaries of a single keysimultaneously with other sets of characters on adjacent keys of avirtual keyboard.

FIGS. 3-9 illustrate a series of example front views of the touchscreen118 having a virtual keyboard 320, consistent with example embodimentsdisclosed herein. Starting with FIG. 3A, touchscreen 118 includes avirtual keyboard 320 that is touch-active. The position of the virtualkeyboard 320 is variable such that virtual keyboard 320 can be placed atany location on touchscreen 118. Touchscreen 118 could be configured todetect the location and possibly pressure of one or more objects at thesame time. Touchscreen 118 includes two areas: (1) an input field 330that displays characters after a user has inputted those characters and(2) the virtual keyboard 320 that receives the input from the user. Asdescribed throughout this disclosure, a virtual keyboard displays a setof characters at a location on the keyboard corresponding to asubsequent candidate input character that might be received as inputfrom the user.

The examples and embodiments illustrated in FIGS. 3-9 can be implementedwith any set of characters, such as words, phrases, acronyms, names,slang, colloquialisms, abbreviations, or any combination thereof.

As shown in FIG. 3A, touchscreen 118 displays a standard QWERTY virtualkeyboard 320; however, any conventional key configuration can bedisplayed for use in the device, such as AZERTY, QWERTZ, or a layoutbased on the International Telecommunication Union (ITU) standard (ITUE.161) having “ABC” on key 2, “DEF” on key 3, and so on. Virtualkeyboard 320 includes space key 350 as well as other keys that canprovide different inputs, such as punctuation, letters, numbers, enteror return keys, and function keys. While virtual keyboard 320 is shownas having a square shape, it can have any other shape (such as an arch).

As shown in FIG. 3A, touchscreen 118 displays input field 330, whichdisplays the characters the user inputs using virtual keyboard 320.Input field 330 includes a cursor 340, which can be an underscore (asshown) or any other shape, such as a vertical line. Cursor 340represents the character space where a next inputted character, selectedcharacter, or selected set of characters will be inserted.

As shown in FIG. 3B, when a user inputs a character (in this example,“P”), this character is displayed in input field 330 and cursor 340moves to the character space where the next inputted character or wordwill be inserted. After the character is inputted, a predictor (such as,a predictive algorithm or a circuit) can generate set of characters 360(for this embodiment) that all begin with the character “P”, orcharacters if more than one character is input. The generated set ofcharacters are displayed at a location on the keyboard corresponding toa subsequent candidate input character that might be received as inputfrom the user. As mentioned, generated set of characters 360 can bedisplayed at or near the key corresponding to the subsequent candidateinput characters (for example, under the respective A, E, H, and O keysof the virtual keyboard 320). Indeed, slightly shifting the displaylocation of the generated set of characters can address overcrowding ofsubsequent candidate input characters, effectively permitting more setof characters to be displayed.

In the example shown in FIG. 3B, “P” is received as input and apredictor generates several set of characters 360, which are displayedat keys corresponding to each generated set of characters' subsequentcandidate input character. As shown in FIG. 3B, “People” is placed atthe “E” key because the next letter after “P” of “People” is “E”; “Paul”will be place at the “A” key because the next letter after “P” of “Paul”is “A”; “Phone” will be placed at the “H” key because the next letterafter “P” of “Phone” is “H”; and so on. It should be noted that any ofthe letters in the set of characters can be upper case or lower case.

In the embodiment shown in FIG. 3C, “L” is next input received bytouchscreen, and a predictor determines several generated set ofcharacters 360, which are displayed at a key corresponding to subsequentcandidate input characters (for example, under the respective A, E, andU keys of the virtual keyboard 320), for the current position of cursor340, which is in the third character position, as shown in input field330. In another embodiment, a generated set of characters 360 can bepresented such as to include the subsequent candidate input character.For example, the set of characters “Please” can be displayed so that thecharacters “Pl.” are displayed before the “E” character on the “E” key,and the characters “ase” can be placed after the “E” character on the“E” key. Further, in this or other embodiments, the displayed “E” can bepresented in a manner that differs from the “Pl” and “ase”, therebyenabling the user to still recognize it as the “E” key while also makingit readily visible so that the user can either input the generated setof characters “Please” or input the character “E”. The “E” can becapitalized or in lowercase. In other embodiments, an affix can bedisplayed at the key. Using the example of the set of characters“Please” above, the “ase” could be displayed at the “E” key so the setof characters fragment “-ease” or “-Ease” would appear.

If the user inputs a generated set of characters, that set of charactersis placed in input field 330. This can be seen in FIG. 3D, where theuser has inputted generated set of characters “Please,” resulting in itsplacement in the input field. A space is inserted after the set ofcharacters if the user wants to input a new set of characters. A usercould input a generated set of characters in various ways, including ina way that differs from a manner of inputting a character key. Forexample, to input a generated set of characters, a user could use afinger or stylus to swipe the generated set of characters. As usedherein, swiping includes swiping the set of characters itself or swipingor touching near the set of characters. For the latter embodiment, thedevice can detect a swipe or touch near a set of characters, be it agenerated set of characters or a predicted set of characters (to bedescribed below), and through the use of a predictor, determine the setof characters the user intended to input. In another embodiment, theuser could press a key for a predetermined period of time, such as along press. That key can be, for example, the key corresponding to thesubsequent candidate input character of the set of characters. So, ifthe set of characters “Please” is intended to be inputted instead of“E”, the electronic device 100 can be configured to require that the “E”key be pressed for a predetermined period of time to trigger the inputof “Please”.

After a generated set of characters 360 has been determined, as shown inFIG. 3D, a predicted set of characters 380 can be displayed, shown hereat space key 350. Predicted set of characters 380 can differ fromgenerated set of characters 360 (as shown in FIGS. 3A-3C) and is thesystem's attempt to predict the next set of characters a user might becontemplating. A predictor is used to determine predicted set ofcharacters 380. As with displayed generated set of characters 360,predicted set of characters 380 can be received as input in any numberof ways, including receiving a swiping of the predicted set ofcharacters with a finger or stylus or receiving a pressing of a key(such as the space key or another designated key) for a predeterminedperiod of time (long press).

In FIG. 4A, electronic device 100 receives “C” as input from virtualkeyboard 320. Again, a predictor determines generated set of characters460 based in part on the received input. In FIG. 4B, electronic device100 receives “O” as input from the virtual keyboard and outputs the “O”in input field 330. As shown in FIG. 4A, the set of characters “count”was displayed at the “O” key after the input of the “C” character wasreceived. Since the “O” key was pressed in a manner to only input the“O” character, as shown in FIG. 4B, an “O” is displayed as secondcharacter of the currently inputted set of characters, and the set ofcharacters “count” is not inputted by the user. Alternatively, if a userwanted to input the generated set of characters “count,” the user caninput the “O” key in FIG. 4A in a manner different from a manner ofinputting the “O” key, such as by swiping the set of characters “count”or by a long press on the “O” key, as opposed to tapping. Returning toFIG. 4B, after the “O” is inputted, generated set of characters 460 aredisplayed at the keys corresponding to subsequent candidate inputcharacters, as shown in FIG. 4B.

FIG. 5 shows input field 330 displaying the set of characters “contact”followed by a space. In that instance, the user inputted the generatedset of characters “contact” 460 as was shown in FIG. 4B at the “N” key.Referring back to FIG. 5, a <SPACE> character is now automaticallyinserted after the generated word in the input field. Predicted word“me” 580 is now displayed on space key 350.

If the predicted word “me” 580 is received as input, the word “me” 580is then displayed in input field 330 followed by a space as shown inFIG. 6A, which then shows predicted word 680 “immediately” displayed onspace key 350. The predicted word is presented after a completed wordand space have been displayed in input field 330.

FIG. 6B shows an example where touchscreen 118 has received the “T”character as input after the user has pressed the “T” key. In thisscenario, touchscreen 118 displays a “t” in input field 330. Generatedset of characters 660 (for example, “Tuesday,” “today,” and “Thursday”)are displayed at the keys of the subsequent candidate input characters.FIG. 6C shows an example where electronic device 100 has received the“o” character as input after the user presses the “O” key instead ofinputting generated set of characters 660 “today” as was shown in FIG.6B. Thus, “o” is now displayed in input field 330.

FIG. 7 shows an example where touchscreen 118 has received the <SPACE>character as input after the user selects the space key. In thisscenario, touchscreen 118 inserts a <SPACE> character, and then displayspredicted set of characters “talk” 780 at space key 350.

FIG. 8A shows an example where touchscreen 118 has received the “d”character as input after the user presses the “D” key. In this scenario,touchscreen 118 displays a “d” in the input field 330 and displaysgenerated set of characters “discuss,” “divide,” and “dinner” 860 onkeys corresponding to subsequent candidate input characters. In thisexample embodiment, while the character “I” was never received as input,electronic device 100 determined that generated set of characters“discuss,” “divide,” and “dinner” 860 were the set of characters to bedisplayed on touchscreen. In this embodiment, because each of these setof characters has “i” as its second letter, touchscreen 118 displayedgenerated set of characters using a further subsequent letter in the setof characters (for example, “discuss” under the “S” key, “divide” underthe “V” key, and “dinner” under the “N” key). In other embodiments,generated set of characters “discuss,” “divide,” and “dinner” 860 can bedisplayed at or near the “I” key.

FIG. 8B shows an example where touchscreen 118 has received the set ofcharacters “discuss” as input after the user chooses generated set ofcharacters “discuss” 860. In this example, touchscreen 118 displayspredicted set of characters “this” 880 at space key 350.

FIG. 9 shows an example where touchscreen 118 receives the “this” set ofcharacters as input after user selects “this” as a desired predicted setof characters 880. In this example, touchscreen 118 displays predictedset of characters “now” 980 at space key 350.

Touchscreen 118 can also receive punctuation as input at any time duringthe typing of a message. If a user decides to use punctuation afterinputting either a generated set of characters or a predicted set ofcharacters, the <SPACE> character (for example, the <SPACE> characterprior to cursor 940 of FIG. 9) is deleted and the inputted punctuationis inserted.

FIGS. 10A and 10B show example front views of a touchscreen, consistentwith embodiments disclosed herein. FIG. 10A shows an example wheretouchscreen 118 displays “The co” in a text bar 1030 and severalgenerated set of characters 1060 are displayed at subsequent candidateinput characters. In this example, touchscreen 118 displays generatedset of characters “cottage” 1060 under the “T” key, generated set ofcharacters “cook” 1060 under the “O” key, generated set of characters“coat” 1060 under the “A” key, and generated set of characters “coffee”1060 under the “F” key.

FIG. 10B shows an example where touchscreen 118 receives the set ofcharacters “cook” as input after the user has selected the generated setof characters 1060 “cook.” The set of characters “cook” is inserted intoinput field 1030 along with a <SPACE> character. In this example, set ofcharacters include new predicted set of characters (such as words 1090,affixes 1092 (for example, “-ed” under the “E” key and “-ing” under the“I” key), and plurals 1094 (for example, “-s” under the “S” key)), allof which are displayed at subsequent candidate input characters. Eachpredicted word 1090, affix 1092, or plural 1094 is located on respectivesubsequent candidate input characters that match the first letter of thepredicted word 1090, affix 1092, or plural 1094. Now the user has theadded option of inputting a predicted set of characters 1090, 1092, and1094. Input is made in the same manner as described above. In someembodiments, when touchscreen 118 receives either affix 1092 or plural1094 as an input, the <SPACE> character between cursor 1040 and “cook”is deleted and the corresponding inputted affix or plural is added tothe end of “cook.”

FIG. 11A shows an example where touchscreen 118 displays “Did she co” ina text bar 1130 and several generated set of characters 1160 aredisplayed at subsequent candidate input characters. In this example,touchscreen 118 displays generated set of characters “correct” 1160under the “R” key, generated set of characters “copy” 1160 under the “P”key, and generated set of characters “contact” 1160 under the “N” key.While “co” is provided in the text bars of both FIG. 10A and FIG. 11A,touchscreen displays different generated set of characters based on thecontext of the characters in their respective text bars 1030 and 1130.For example, in FIG. 10A, the characters “co” follows “The,” whichimplies that a noun beginning with “co” should follow. In FIG. 11A, thecharacters “co” follow a pronoun, which implies that a verb beginningwith “co” should follow. As stated above, contextual data can be used todetermine when certain set of characters are more appropriate based on,for example, the set of characters in a text bar or previous actions bya user.

FIG. 11B shows an example where touchscreen 118 receives the set ofcharacters “correct” as input after the user has selected the generatedset of characters “correct” 1160. In this example, the set of characters“correct” is inserted in input field 1130 and a <SPACE> character isalso inserted. Predicted set of characters (such as words 1190 andaffixes 1192) are now displayed at subsequent candidate inputcharacters. In this example, while affixes “-ing” and “-ily” bothcorrespond to the “I” key, touchscreen 118 displays “-ing” with the “I”key and “-ily” with the “L” key. As stated above, the predicted affixmay be assigned to a certain key based on a ranking, on contextual data,or a combination of both. In this embodiment, the “-ing” affix may havehad a higher ranking than the “-ily” affix and was thus assigned to the“I” key. Accordingly, the “-ily” affix was assigned to the “L” key basedon the corresponding “L” character being in the “-ily” affix.

FIG. 12A shows an example where touchscreen 118 displays “The ch” in atext bar 1230 and several generated set of characters 1260 are displayedat subsequent candidate input characters. In this example, generated setof characters 1260 include both “child” and “chimp.” In this embodiment,while the third letter in both “child” and “chimp” are the same,touchscreen displays “child” under the “I” key and displays “chimp”under the “C” key. The determination on which generated set ofcharacters goes under which candidate input key can be based on aranking (as specified above). As illustrated in this embodiment,touchscreen 118 can display a generated set of characters (in this case,“chimp”) on a key even though that key may not be associated with anysubsequent characters of the characters in text bar 1230.

FIG. 12B shows an example where touchscreen 118 receives the set ofcharacters “child” as input after the user has selected the generatedset of characters “child” 1260. The set of characters “child” isinserted in input field 1230 and, in this example, a <SPACE> characteris not inserted. Predicted set of characters (such as words 1290 andaffixes 1292) are now displayed at subsequent candidate inputcharacters. In this example, while affixes “-ish” and “-ily” bothcorrespond to the “I” key, touchscreen 118 displays “-ish” with the “I”key and “-ily” with the “L” key. As stated above, the predicted affixmay be assigned to a certain key based on a ranking, on conventionaldata, or a combination of both. In this embodiment, the “-ish” affix mayhave had a higher ranking than the “-ily” affix and was thus assigned tothe “I” key. Accordingly, the “-ily” affix was assigned to the “L” keybased on the corresponding “L” character being in the “-ily” affix.

FIG. 13A shows an example where touchscreen 118 displays “The textureand” in a text bar 1330 and several predicted set of characters (forexample, words 1390) are displayed at subsequent candidate inputcharacters. FIG. 13B shows an example where touchscreen 118 received theset of characters “taste” as input after the user had selected thepredicted set of characters “taste.” In this example, a <SPACE>character was inserted after “taste.” Consequently, predicted set ofcharacters (such as, words 1390 and affixes 1392) are displayed atsubsequent candidate input characters.

FIG. 14A shows an example where touchscreen 118 displays “The hospitalstaff c” in a text bar 1430 and several generated set of characters 1460are displayed at subsequent candidate input characters. FIG. 14B showsan example where touchscreen 118 received the set of characters “care”as input after the user had chosen the generated set of characters“care.” Generated set of characters “care” is now placed in input field1430 along with a <SPACE> and predicted set of characters (such as,words 1490 and affixes 1492) are displayed at subsequent candidate inputcharacters. FIG. 14C shows an example where touchscreen 118 received theaffix “-ful” as input (thereby modifying the set of characters “care” to“careful”) after the user had chosen the predicted affix “-ful.” Thus,the set of characters “careful” is now inserted into input field 1430.Note, in some embodiments, inputting a word or affix can modify theinput word or word fragment. For example, if “spicy” was input by auser, and “ness” is a predicted affix and is inputted, “spicy” wouldchange to “spiciness,” dropping the “y” and adding “iness”. In otherembodiments, “happy” could change to “happiness” or “conceive” couldchange to “conceivable”.

FIG. 15 shows an example of an ambiguous keyboard 1520, which can havemultiple characters assigned to a key (for example, such as a telephonekeypad where “A”, “B” and “C” are assigned to key 2; “D”, “E” and “F”are assigned to key 3, and so on). For example, the characters “Q” and“W” can be assigned one key, and the characters “E” and “R” assigned toanother key. In this example, the user has input the characters “01” bypressing the “op” key followed by the “L” key. Using a predictor,generated set of characters 1560 are displayed at subsequent candidateinput characters. Since the first pressed key can input either an “O” ora “P” and the second pressed key inputs an “L”, generated set ofcharacters 1560 will begin with “OL” or “PL”, such as shown by generatedset of characters 1560 in FIG. 15.

FIG. 16 shows another example of an ambiguous keyboard 1620. In thisexample, generated sets of characters “plum” and “olive” 1660 aredisplayed near the “ui” key. The sets of characters could also have beendisplayed at or on the “ui” key. Here, both sets of characterscorrespond to a particular input corresponding to a key, namely thethird letter of plum is a “u” and the third letter of olive is an “i.”Touchscreen 118 (via main processor 102) can differentiate between theinput of either set of characters based on the user's action. Forexample, the user can swipe at or near the right of the “ui” key toinput “olive”, or swipe at or near the left of the “ui” key to input“plum”.

The examples and embodiments illustrated in FIGS. 17, 18, and 19 can beimplemented with any set of characters such as words, phrases, acronyms,names, slang, colloquialisms, abbreviations, or any combination thereof.

FIG. 17 shows in flowchart form a method 1700 in accordance with someembodiments. Method 1700 can be implemented with a processor, such asmain processor 102, and stored on a tangible computer readable medium,such as hard drives, CDs, DVDs, flash memory, and the like. At block1710, the processor receives an input of a character. At block 1720, theprocessor displays a generated set of characters at or near keys ofsubsequent candidate input characters on the touchscreen, such asdescribed above.

At block 1730, the processor receives an input of the generated set ofcharacters chosen by a user. If the user does not choose a generated setof characters displayed at or near keys of subsequent candidate inputcharacters, the method restarts at block 1710, where the touchscreen canreceive an input of another character. If a generated set of charactersis received as input, at block 1740 the generated set of characters anda <SPACE> character is inserted in an input field (for example, inputfield 330 of FIGS. 3-9). As mentioned previously, the user can choosethe generated set of characters, for example, by swiping at or near itor by long pressing a key corresponding to the subsequent candidateinput character.

Continuing at block 1750, if the processor detects that punctuation isnot to be inserted, the method restarts at block 1710. If punctuation isto be inserted, the method continues to block 1760 where the <SPACE>character is deleted and the appropriate punctuation is added to theinput field. After block 1760, the method starts over at block 1710.

FIG. 18 is a flowchart illustrating example method 1800 in accordancewith some embodiments. Method 1800 can be implemented with a processor,such as main processor 102, and stored on a tangible computer readablemedium, such as hard drives, CDs, DVDs, flash memory, and the like. Atblock 1810, the processor receives an input of a character.

At block 1820, the processor displays a generated set of characters ator near a location on the keyboard corresponding to a subsequentcandidate input character on a touchscreen. At block 1830, the processorreceives an input of a generated set of characters chosen by a user. Ifthe user does not choose a generated set of characters displayed at ornear keys of subsequent candidate input characters, the method restartsat block 1810, where the processor can receive an input of anothercharacter. If a generated set of characters is received as input, atblock 1840 the generated set of characters and a <SPACE> character isinserted in an input field (for example, input field 330 of FIGS. 3-9).As mentioned previously, the user can choose the generated set ofcharacters, for example, by swiping at or near it or by pressing a keycorresponding to the subsequent candidate input character for apredetermined period of time.

At block 1850, a predicted set of characters, different from thegenerated set(s) of characters, is displayed on a space key of thekeyboard after the input of the generated set of characters in block1830. The predicted set of characters displayed in block 1850 isdetermined by using a predictor. In some embodiments, the one or morepredicted sets of characters can be placed on one or more keys otherthan the space key.

At block 1860, the processor can determine whether it has received aninput of the predicted set of characters based on a user input. If thetouchscreen has not received an input of the predicted set of charactersbecause the user has not chosen the predicted set of characters, themethod restarts at block 1810. If the processor has received the inputof the predicted set of characters, the method continues to block 1870,where the chosen predicted set of characters and a <SPACE> character isinserted in the input field. From here, method 1800 can return to eitherblock 1810 or block 1850.

Even though method 1800 does not display the punctuation illustration asshown in method 1700, the punctuation illustration, as shown in blocks1750 and 1760, can likewise be applied to method 1800.

FIG. 19 is a flowchart illustrating an example method 1900 in accordancewith some embodiments. At box 1910, predicted set of characters isdisplayed at corresponding subsequent candidate input characters. Inthese embodiments, an input has not been received or a delimiter hasbeen activated, such as inputting a <SPACE>. Here, one or more predictedset of characters (such as, words, affixes, or a combination thereof)are placed on subsequent candidate input characters that correspond tothe first letter of the generated set of characters. Moving to box 1920,it is determined whether the touchscreen receives an input of the set ofcharacters (such as, word or affix) based on a user's selection. If aninput is received, the method moves to block 1930 where the predictedset of characters and a <SPACE> character are inserted into an inputfield. Then the method starts over at block 1910. If the touchscreendoes not receive an input of the set of characters, the touchscreen isavailable to receive an input of a character (as described by block 1710of FIG. 17 or block 1810 of FIG. 18) and proceed through methods (suchas methods 1700 of FIG. 17 or 1800 of FIG. 18 or even method 1900 ofFIG. 19).

FIG. 20 shows another example of a virtual keyboard 2020 having an inputfield 2030. The set of characters “Please con” are received as input bythe touchscreen and displayed in the input field 2030 followed by acursor 2040, which can be a vertical line (as shown) or any other shape,such as an underscore as mentioned previously. A predictor determinesone or more generated set of characters 2060 based in part on thereceived input for the current position of cursor 2040 within thecurrent word, which is in the fourth character position of the currentword, as shown in input field 2030. The current word is the word inwhich the cursor is currently located. In the shown example, generatedset of characters 2060 “cones”, “contact”, “construction” and “connect”are displayed. Each generated set of characters 2060 is displayed at akey corresponding to a subsequent candidate input character (forexample, under the E, T, S and N keys of the virtual keyboard 2020,respectively), for the current position of cursor 2040, which is in thethird character position, as shown in input field 2030.

In the shown example, each generated set of characters 2060 is displayedat or near keys on the virtual keyboard 2020 associated with thesubsequent candidate input characters. The display of a generated set ofcharacters 2060 at or near a key corresponding to a subsequent candidateinput character depends, for instance, on the size of the generated setof characters 2060 and the size of generated set of charactersassociated with nearby keys of other subsequent candidate inputcharacters. When the generated set of characters associated with nearbykeys in the same row of keys in the virtual keyboard 2020 are too largeto be displayed at the same time without overlapping with each other orwithout a predetermined distance between the generated sets ofcharacters, the processor 102 limits the generated set of characterswhich are displayed. The processor 102 may limit the generated set ofcharacters which are displayed using one or any combination of the rankof each generated set of characters, the size of each generated set ofcharacters, and a distance between each generated set of characterswhich are displayed so that a predetermined distance between thegenerated set of characters is maintained. This may result in thedisplay of one or more generated sets of characters which are largerthan the associated key in the virtual keyboard 2020.

In some examples, if two generated sets of characters are both rankedhigh, and these sets of characters would otherwise be displayed atnearby keys but cannot be displayed and still maintain a predetermineddistance between the generated sets of characters at the display textsize, the electronic device could be configured to display only thehighest ranked generated set of characters. This results in the displayof the most likely generated set of characters. In other examples, onlythe longest of the generated set of characters is displayed. This may bebeneficial in that allowing faster entry of longer words saves time andprocessing cycles, thereby leveraging the predictive text inputsolution. In yet other examples, only the shortest generated set ofcharacters is displayed. This may be beneficial in that shorter wordscan be more common, at least for some users, thereby allowing fasterentry of words which saves time and processing cycles, therebyleveraging the predictive text input solution.

In some examples, the processor 102 may only limit the generated set ofcharacters which are displayed in neighboring/adjacent keys in the samerow of keys in the virtual keyboard 2020. In some examples, theprocessor 102 may limit the generated set of characters which aredisplayed in neighboring/adjacent keys in the same row of keys in thevirtual keyboard 2020 so that a generated set of characters is neverdisplayed in neighboring/adjacent keys irrespective of the size of thegenerated set of characters or distance between each generated set ofcharacters. In such examples, the processor 102 uses the rank todetermine which generated set of characters are displayed.

In other examples, the processor 102 can limit the generated set ofcharacters which are displayed when the generated set of charactersassociated with nearby keys in different rows of keys in the virtualkeyboard 2020 are too large to be displayed at the same time withoutoverlapping with each other or without a predetermined distance betweenthe generated sets of characters. In other examples, the processor 102can limit the generated set of characters which are displayed when thegenerated set of characters associated with nearby keys in the same ordifferent columns of keys in the virtual keyboard 2020 are too large tobe displayed at the same time without overlapping with each other orwithout a predetermined distance between the generated sets ofcharacters

As mentioned previously, a user can use a finger or stylus to swipe agenerated set of characters to input that generated set of characters.An individual letter, in contrast, can be input by tapping a respectivekey in the virtual keyboard 2020 using a finger or stylus. Thetouchscreen differentiates between tap and swipe events using movementand duration of touch events, the details of which are known in the artand need not be described herein. Each key in the virtual keyboard 2020and each generated set of characters 2060 which is displayed has anassociated target area on the touchscreen. The target area associatedwith each generated set of characters can be larger than and/or overlapwith the target area of the key corresponding to the subsequentcandidate input character with which it is associated and possiblynearby keys, such as neighboring keys in the same row. A user need onlyswipe on or nearby a displayed generated set of characters to input thegenerated set of characters. This permits faster input of a generatedset of characters by creating larger and more accessible target areas,thereby saving time and processing cycles. In some examples, a generatedset of characters can be input by detecting a swipe in any direction ator near the displayed generated set of characters. In other examples, agenerated set of characters can only be input by detecting a swipe in aparticular direction at or near the displayed generated set ofcharacters. The particular direction may be associated with a directionin which the particular direction displayed generated set of characters(e.g., left or right in the shown example). In some examples, the swipeis at or near the displayed generated set of characters when the swipehas an initial contact point within the target area associated with thedisplayed generated set of characters (which may be the same or largerthan the displayed generated set of characters).

When inputting characters, users may hold the device in both hands usingonly their thumbs to activate the keys on the virtual keyboard.Two-thumb typing is common in landscape screen orientations but may alsobe used in portrait screen orientations (typically only when the size ofthe touchscreen 118 is sufficiently large). Referring to FIG. 21, anexample virtual keyboard 2120 having a number of keys 2130 is shownalong with a user's thumbs 2150A and 2150B, respectively.

As illustrated in FIG. 21, a user's thumbs 2150A and 2150B may obscurelarge portions of the virtual keyboard 2120 from the user's eyes. Insome instances, this may make it difficult for the user to discernwhether he/she has activated the desired key. In some electronicdevices, the activated key will flash or a visual cue such as a tooltipmay be displayed above the activated key to inform the user of which keyhas been activated. As appreciated by persons skilled in the art, atooltip is a user interface element provided by the GUI which provides ahint associated with another user interface element. The hint provides avisual cue directing the user's attention to the other user interfaceelement. Tooltips used in conventional virtual keyboards are displayedabove the activated key in the virtual keyboard. The tooltip typicallyhovers above the activated key for a short duration, typically while thecontact with the activated key on the touchscreen 118 is maintained(e.g., the tooltip disappears/is removed when the user lifts his/herfinger. In one example as seen in FIG. 21, if the user is activating the“N” key with the right thumb 2150B, the user's thumb may obscure theflash of the “N” key or the display of a tooltip above the “N” key.Accordingly, conventional tooltips are limited in the extent to whichthe notification function of the tooltips is effective.

FIG. 22 shows in flowchart form a method 2200 in accordance with someexample embodiments. The example method 2200 and any methods describedherein can be implemented with a processor, such as main processor 102,and stored on a tangible computer readable medium, such as hard drives,CDs, DVDs, flash memory, and the like.

At block 2210, the device detects a touch input at a key 2130 of thevirtual keyboard 2120. In some examples, the touch input may be a tap ora prolonged touch on or around a key 2130 of the virtual keyboard 2120.In some examples, the touch input may be one of the contact points of amulti-touch input.

At block 2220, the device determines an input direction of the touchinput. The input direction of the touch input is a direction from whichthe device determines a user has provided the touch input. For example,when a user is holding a device in the manner illustrated in FIG. 21,the user's left thumb 2150A will likely approach and provide a touchinput from the left side of the virtual keyboard 2120. Accordingly, thedetermined input direction in such cases is left. Conversely, the user'sright thumb 2150B will likely approach and provide a touch input fromthe right side of the virtual keyboard. Accordingly, the determinedinput direction in such cases is right.

As described above, in at least some examples, the input direction maybe left or right of the virtual keyboard. In some examples, the inputdirection may be top or bottom of the virtual keyboard. Other inputdirections are also possible, such as a diagonal direction, which may beat any angle.

The input direction may be determined in accordance with the directionof a touch input, such as the direction in which a contact point movesafter initially contacting the touchscreen 118, the shape of the contactarea of the touch input, the proximity of the touch input to arespective edge of the touchscreen 118, or other suitable means,examples of which are provided below. The proximity of the touch inputmay be determined relative to a screen orientation of the GUI (e.g.,input is closest to left, right, top or bottom of the virtual keyboard2120). Alternatively, the proximity of the touch input may be determinedrelative to the touchscreen 118 (e.g., input is closest to left, right,top or bottom of the touchscreen 118).

At block 2230, a visual cue of the key at which the touch input wasdetected is displayed on the display. This visual cue is displayed at aposition on the display based on the input direction of the touch input.In some examples, the visual cue is displayed proximate to the touchedkey and offset in a direction away from the input direction of the touchinput.

In some examples, the input direction provides a proxy for determiningwhich of the user's hands is being used, i.e. to which hand the fingercausing the touch input belongs, so that the visual cue may be locatedaccordingly. When the touch input is associated with the user's lefthand, the visual cue is located to the right of the activated key(typically above and to the right of the activated key). When the touchinput is associated with the user's right hand, the visual cue islocated to the left of the activated key (typically above and to theleft of the activated key).

FIG. 23 shows an example of a virtual keyboard 2120 on which a userprovides a touch input on the “X” key with the user's left thumb 2150A.The device determines that the input direction of the touch input isfrom the left side of the device. The device displays a visual cue inthe form of a character icon 2350 showing that the “X” key has beentouched. Based on the left input direction of the touch input, thedevice displays the “X” character icon 2350 proximate but offset to theright of the “X” key. In other words, in this example, the visual cue isoffset in a direction away from the input direction. In some instances,by displaying the visual cue in this manner based on the input directionof the touch input, the chance of the visual cue being obscured by aninput implement may be reduced, and in some instances, the visibility ofthe touch input feedback to the user may be improved.

Generally, a user's eyes are above the user's hands relative to thedevice. Therefore, in some examples including the example in FIG. 23,the visual cue is offset above and in a direction away from the inputdirection. In FIG. 23, the visual cue in the form of character icon 2350is offset above and to the right of the touched “X” key. In someexamples, additionally offsetting the visual cue in a direction abovethe touch input will reduce the chance of the visual cue being obscured,and in some examples may increase the visibility of the visual cue tothe user. In some examples, discussed in more detail below, the visualcue (e.g., tooltip) may be selectable. For example, tapping the visualcue may cause an action associated with the visual cue, such as acharacter input, to be performed. In such examples, it is easier for afinger in the opposite hand to select the visual cue (e.g., tooltip) ifthe visual appears in the direction of the opposite hand. For example,in FIG. 23, if the character icon 2350 for the ‘X’ key was an actionableitem, the directional bias would make it easier for the right hand thumbto tap the character icon 2350 to input the character “x” or perform acommand associated with the “X” key.

FIG. 24 shows another example of a virtual keyboard 2120 on which a useris providing a touch input on the “U” key with the user's right thumb2150B. In this example, the device detects the touch input anddetermines that the input direction of the touch input is from theright. Based on this input direction, the device displays a visual cuein the form of a “U” character icon 2350 which is offset above and tothe left of the touched “U” key.

In some examples, the visual cue is displayed for a short durationbefore disappearing again. In some examples, the visual cue is displayedfor as long as the touch input is maintained at the key. For example, ifa user presses and holds a key, the visual cue may remain displayed onthe display until the user releases the key.

As mentioned above, in some examples, the input direction may bedetermined in accordance with the shape of the contact area of the touchinput. As part of the determining the input direction in such examples,the device determines a shape of the contact area of the touch input.Each touch input is caused by a touch event detected by the touchscreen118. The touch event is defined by a contact area caused by interactionof a user's finger or stylus with the touchscreen 118. The touchscreen118, or the main processor 102, may determine a shape or profile of thecontact area of the user's finger.

Referring now to FIG. 25, a Cartesian (two dimensional) coordinatesystem suitable for mapping locations of the touchscreen 118 anddetermining a shape of the contact area of the user's finger will bedescribed. The touchscreen 118 defines a Cartesian coordinate systemdefined by x and y-axes in an input plane of the touchscreen 118. The xand y-axes of the Cartesian coordinate system are used to map locationsof the touchscreen 118 and are aligned with the x and y-axes of thepositional sensor; however in other embodiments these may be different.Each touch event on the touchscreen 118 returns a touch point defined interms of an (x, y) value. The returned touch point is typically thecentroid of the contact area. In the shown embodiment, the coordinatesystem has an origin (0, 0) which is located at a bottom-left corner ofthe touchscreen 118; however, it will be appreciated that the origin (0,0) could be located elsewhere such as a top-left corner of thetouchscreen 118.

The contact area caused by a user's finger roughly represents anellipse. In at least some examples, the touchscreen 118, or the mainprocessor 102, may determine an input direction based on the shape ofthe contact area of the user's finger by performing a mathematicalanalysis on the contact area. As part of calculating performed in themathematical analysis, a center point (or centroid) of the contact areaand two lines which symmetrically bisect the ellipse through the centerpoint are determined. The longer of the bisectors represents a majoraxis (A) of the ellipse and the shorter of the bisectors represents aminor axis (B) of the ellipse. The angle (θ) of the major axis (A)relative to an edge of the display 112 or a screen orientation may beused to determine the direction of the touch input. The screenorientation of the content displayed on the display 112, which is aparameter of the GUI and known to the device, or a device orientation ofthe display 112 which is detected by the orientation sensor 197, may beused to determine the direction along the major axis (A). More detailsof an example method of calculating a shape of the contact area of theuser's finger is found in U.S. Patent Publication No. 2007/0097096,which is incorporated herein by reference.

The centroid of the contact area is calculated based on raw location andmagnitude data (e.g., capacitance data) obtained from the contact area.The centroid is typically defined in Cartesian coordinates by a value(X_(c), Y_(c)). The centroid of the contact area is the weightedaveraged of the pixels in the contact area and represents the centralcoordinate of the contact area. By way of example, the centroid may befound using the following equations:

$\begin{matrix}{X_{c} = \frac{\sum\limits_{i = 1}^{n}{Z_{i}*x_{i}}}{\sum\limits_{i = 1}^{n}Z_{i}}} & (1) \\{Y_{c} = \frac{\sum\limits_{i = 1}^{n}{Z_{i}*y_{i}}}{\sum\limits_{i = 1}^{n}Z_{i}}} & (2)\end{matrix}$

where X_(c) represents the x-coordinate of the centroid of the contactarea, Y_(c) represents the y-coordinate of the centroid of the contactarea, x represents the x-coordinate of each pixel in the contact area, yrepresents the y-coordinate of each pixel in the contact area, Zrepresents the magnitude (e.g., capacitance value) at each pixel in thecontact area, the index i represents the pixel (or electrode) in thecontact area and n represents the number of pixels (or electrodes) inthe contact area. Other methods of calculating the centroid will beunderstood to persons skilled in the art.

In other examples, the touchscreen 118, or the main processor 102, maydetermine an input direction based on the shape of the contact area ofthe user's finger by performing a comparative analysis on the contactarea. As part of the comparative analysis, the detected contact area iscompared to one or more touch profiles stored, for example, in thememory 110 on the device. In some examples, the touch profiles mayinclude common shapes of touch inputs by a left thumb press or rightthumb press. In some examples, profiles may also include common shapesfor left or right finger touches. In some examples, these profiles mayinclude common shapes of stylus touches when held by a left hand or whenheld by a right hand.

In some examples, the device determines the input direction of a touchinput by determining whether the shape of the touch input corresponds toone of the touch profiles stored in memory. For example, if the devicedetermines that a touch input shape corresponds to a touch profile for aleft thumb press, the device may determine that the input direction ofthe touch input is from the left.

The shape of the touch input does not necessarily have to identicallymatch a touch profile. In some examples, the device may determine thecorresponding touch profile by selecting the touch profile which mostclosely resembles the shape of the touch input.

FIG. 26 illustrates non-limiting example touch shapes of a left thumbtouch 2450A and a right thumb touch 2450B. The touch shapes have beenshown as ellipses for illustrative purposes; however, the shape ofactual contact areas may vary. In other examples, the device maydetermine the input direction of the touch input based on which portionof the device the touch input was received. In some examples, if thetouch input is detected on a left portion of the virtual keyboard, thedevice determines that the input direction of the touch input is fromthe left. Similarly, in some examples, if the touch input is detected ona right portion of the virtual keyboard, the device determines that theinput direction of the touch input is from the right.

FIG. 27 shows an example virtual keyboard 2120 having a number of keysin a left portion 2710 and a number of keys in a right portion 2720. Adifferent number of divisions of the keyboard may be used in otherexamples. In some examples, the keys may be assigned into upper andlower portions instead of, or in addition to, the left portion 2710 andthe right portion 2720.

FIG. 28 shows an example virtual keyboard 2120 having keys in a leftportion 2810, a right portion 2820, a mid-left portion 2830, and amid-right portion 2840. In some examples, a touch input at a key in theleft portion 2810 may cause the electronic device 100 to display avisual cue above and to the right of the touched key at an offset ndegrees (e.g., 45 degrees) from the vertical, while a touch input at akey in the mid-left portion 2830 may cause the electronic device 100 todisplay a visual cue above and to the right of the touched key at anoffset m degrees (e.g., 30 degrees) from the vertical, where n and inare different. Similarly, a touch input at a key in the right portion2820 may cause the electronic device 100 to display a visual cue aboveand to the left of the touched key at an offset n degrees (e.g., 45degrees) from the vertical, while a touch input at a key in themid-right portion 2840 may cause the electronic device 100 to display avisual cue above and to the left of the touched key at an offset indegrees (e.g., 30 degrees) from the vertical, where n and are different.Accordingly, the offset distance and/or position between the touched keyand the visual cue may vary based on which portion the activated key islocated in. This solution allows the offset distance and/or position tomore precisely adjust to the position of the user's finger.

In some examples, when a touch input is detected in a middle portion ofthe virtual keyboard such as mid-left 2830 and mid-right 2840 portionsillustrated in FIG. 28, the electronic device 100 may display a visualcue offset such that it is directly above the touched key.

In some examples, when a touch input is detected in a middle portion ofthe virtual keyboard (such as mid-left 2830 and mid-right 2840 portionsillustrated in FIG. 28, such as mid-left 2830 and mid-right 2840portions illustrated in FIG. 28), the electronic device 100 may displaya visual cue offset in a direction away from the next most probableletter based on letter or word predictions, as mentioned previously.

In some examples, the electronic device 100 may determine the inputdirection of the touch input, at least in part, by detecting proximityinformation on the one or more proximity sensor 198 or detecting ambientlight information on the one or more ambient light sensors 199. Theelectronic device 100 detects proximity of an object at or near thedisplay 112 at a time when the touch input was detected (using proximityinformation and/or ambient light information), and determines the inputdirection as left or right in accordance with a side of the display atwhich proximity of an object was detected. In some examples, a firstproximity sensor 198 on a left side of the electronic device 100 and asecond proximity sensor 198 on the right side of the electronic device100 may detect the proximity of a user's hand approaching from the leftor right side of the electronic device 100. In some examples, a singleproximity sensor 198 at a central position on the electronic device 100may be configured to detect objects in close proximity to either theleft or the right sides of the electronic device 100. In some examples,the one or more proximity sensors 198 may also detect the proximity ofan object close to the top or bottom of the electronic device 100. Inany of these examples, the proximity of an object to a particular sideof the electronic device 100 may correspond to a determination that atouch input is coming from that particular side of the electronic device100.

Similar to the proximity sensor examples described above, the ambientlight sensor 199 may detect proximity of an object at or near thedisplay 112 in accordance with a lower intensity ambient light at aparticular side of the electronic device 100. In some examples, thelower intensity ambient light may correspond to a shadow cast by anobject approaching from that particular direction, and may thereforecorrespond to a determination that a touch input is coining from thatdirection.

In some examples, the electronic device 100 may determine the inputdirection of the touch input, at least in part, by detecting theorientation of the electronic device 100 using an orientation sensor 197such as an accelerometer. In some examples, the electronic device 100may determine that the electronic device 100 is lying on a flat surfacesuch as a desk when the orientation sensor 197 detects that theelectronic device 100 is horizontal with the face of the touchscreen 118facing upwards. With this information, the electronic device 100 maydetermine that touch input corresponds to a finger other than the user'sthumbs because it would be difficult for a user to use his/her thumbswhen the device is lying on a flat surface. In such cases, any analysisof the shape of the contact area of the touch input may be restricted tofingers other than the thumbs, and may be restricted to index fingers,which are typically used for typing when using the electronic device100. This allows, for example, shape analysis to be limited to a subsetof data, such as fingers other than thumbs or merely index fingers.

In some examples, the orientation sensor 197 may detect that theelectronic device 100 is partially upright with the top of theelectronic device 100 facing upwards and slightly to the right. In thisorientation, a user may be holding the device only in his/her righthand, and therefore, a user may likely be using his/her right hand toprovide touch inputs. Accordingly, the device may use the detectedorientation information to determine that a touch input is from theright side of the electronic device 100. Similarly, in some examples,the orientation sensor 197 may detect that electronic device 100 is in aposition which may correspond to a user holding the electronic device100 only in his/her left hand, and therefore, the electronic device 100may use the detected orientation information to determine that a touchinput is from the left side of the electronic device 100.

Other techniques may be used alone or in conjunction with othertechniques to determine the finger input direction and/or where thevisual cue (e.g., tooltip) should be located. For example, settings maybe used. The electronic device 100 may allow users to specify whichfinger he or she uses for which key. This may be useful to adjust amapping model which, for example, may have been learned by theelectronic device 100 through other means. For example, the electronicdevice 100 may determine that a left-hand finger is being used when thecharacter ‘g’ is typed and a right-biased visual cue (e.g. tooltip)appears whereas the user may want the tooltip direction to be biased tothe left because the user uses the right-hand finger when the character‘g’ is typed or for other reasons. A settings menu to modify thebehaviour of the visual cues may be useful. Finger mapping may also beused. Finger mapping, i.e., which finger tapped which character key in aparticular context, may be learned from an external camera-based systemwhich analyses the virtual keyboard or other means.

While the foregoing description in connection with FIG. 21-28 has beenfocused on two-finger typing, the teachings of the present disclosurecan also be applied to one-finger typing. One-finger typing (e.g.,one-thumb typing) is typically performed when users hold the device inone hand and use only one finger (typically a thumb) to activate thekeys on the virtual keyboard. One-thumb typing is common in portraitscreen orientations but may also be used in landscape screenorientations (typically only when the size of the touchscreen 118 issufficiently small).

The device may be able to detect one-finger typing, for example, by theshape of the touch inputs as described previously. The direction/angleof the major axis of the contact area of touch inputs can be used toidentify the handedness of the user, or at least the hand with which theuser is typing. The angle (θ) of the major axis (A) forms an acute anglerelative to a vertical component (y-axis) of the GUI in a given screenorientation as shown in FIG. 25. The angle (θ) is positive relative tothe vertical component when the user is typing with the left hand,whereas the angle (θ) is negative relative to the vertical componentwhen the user is typing with the right hand. When a threshold amount ofdetected touch events are associated with one hand, one-finger typing isdetected. The particular hand with which the touch events are associatedis determined to be the typing hand. One-finger typing may be presumedwhen a portrait screen orientation is used. In such cases, onlyhandedness needs to be determined. Alternatively, handedness may be aknown parameter, for example, a parameter stored in the memory 110.

When left-handed typing is determined or detected, the visual cue islocated to the right of the activated key (typically above and to theright of the activated key). When right-handed typing is determined ordetected, the visual cue is located to the left of the activated key(typically above and to the left of the activated key).

FIG. 29 shows in flowchart form a method 2900 in accordance with someexample embodiments. The example method 2900 described herein can beimplemented with a processor, such as main processor 102, and stored ona tangible computer readable medium, such as hard drives, CDs, DVDs,flash memory, and the like. At block 2910, the device detects a touchinput at a key 2130 of the virtual keyboard 2120 in the form of a touchgesture.

At block 2920, the device determines the input direction of the touchinput. In some examples, the input direction of the touch inputcorresponds to the direction of the touch gesture in relation to aninitial contact point of the touch input.

At block 2930, when the direction of the touch motion corresponds to apeek gesture, a visual cue of a command associated with the key at whichthe touch input was detected (i.e., the activated key) is displayed. Insome examples, the visual cue is displayed proximate to the activatedkey. In some examples, the visual cue is displayed proximate to theactivated key and offset in a direction away from the input direction ofthe touch input as described similar to visual cues describedpreviously.

In some examples, the peek gesture is a small touch gesture having atravel distance which is greater than a first threshold distance butless than a second threshold distance. The use of a small touch gesturein a given direction may be used to differentiate from the touch inputfrom a longer touch gesture in the same direction which is associatedwith another action. The touch gesture, in some examples, may be adownward gesture (such as a downward swipe). In other examples, the peekgesture may be a small upward gesture (e.g., upward swipe). In otherexamples, the peek gesture may be any direction, pattern or combinationof touch gestures such as a circular gesture around the key, or anL-shaped gesture comprising a downward gesture (e.g., swipe) followed bya left-to-right downward gesture (e.g., swipe).

Alternatively, in another embodiment, at block 2930, when the directionof the touch motion corresponds to a peek gesture, a visual cue of analternate character associated with the key at which the touch input wasdetected (i.e., the activated key) is displayed rather than a visual cueof a command associated with the key.

At block 2940, the command associated with the activated key is executedby the device in response to a trigger. Alternatively, in other examplesthe alternate character associated with the key may be input in responseto the trigger. The trigger may be that contact with virtual keyboard2120 is released at or near an end of the peek gesture. In contrast, thecommand associated with the activated key is not executed if the contactpoint is moved back towards its initial position before being released,or is otherwise within a threshold distance of the initial position whencontact with virtual keyboard 2120 is released. In other examples, thetrigger is continuing the peek gesture until a second threshold distancehas been traveled by the touch input. In yet other examples, the triggeris determining a duration of the touch input exceeds a thresholdduration (also known as a touch-and-hold or press-and-hold). Typically,the touch-and-hold or press-and-hold is performed at or near an end ofthe peek gesture.

FIG. 30 shows an example of a virtual keyboard 2120 on which a userprovides a touch gesture on the “R” key. Initially, the user touches thevirtual keyboard 2120 at the initial contact point indicated by thereference 3010. While maintaining contact with the virtual keyboard2120, the user moves the contact point downwards to the contact pointindication by the reference 3020. In this example, the downward touchgesture corresponds to a peek gesture, and the device displays a visualcue in the form of a “reply” command icon 3030 which is associated withthe “R” key. In the shown example, the command icon 3030 is displayedproximate to the associated key. In other examples in which predictedwords are shown in a prediction bar, the command icon 3030 may be shownin the prediction bar.

As mentioned above, after the command icon 3030 is displayed, thecommand (e.g., reply command for replying a received communication suchas an email) associated with the activated key is executed by the devicein response to a trigger.

In the example shown in FIG. 30, the “R” key is associated with the“Reply” command. In the context of messaging, this command may reply toa sender of a currently selected or displayed email message. In someexamples, different keys may be associated with different commands andin different contexts. In a messaging context, in some examples, the “R”key may be associated with the “Reply” command as noted above, the “L”key may be associated with the “Reply All” command to reply to allrecipients of the currently selected or displayed email message, the “F”key may be associated the “Forward” command to forward the currentlyselected or displayed email message, the “S” key may be associated the“Send” command to send an open message under composition, the “N” keymay be associated with a “Next Message” command to display a nextmessage in a list (e.g., inbox or folder), a “P” key may be associatedwith a “Previous Message” command to display a previous message in alist (e.g., inbox or folder), or any combination thereof. Alternatively,the “Send” command for sending an electronic message may be associatedwith an “Enter” key in the virtual keyboard. In a text entry mode, whichmay be in a messaging context, the “Backspace” key may be associatedwith a “Delete” command for deleting an input character at the positionof a cursor in an input field rather than the “Backspace” command fordeleting an input character at a position before the position cursor inthe input field.

In the example described above, a “Reply” command icon associated withthe “Reply” command is displayed when the touch gesture is performed onthe “R” key, a “Reply All” command icon associated with a “Reply All”command is displayed when the touch gesture is performed on the “L” key,a “Forward” command icon associated with a “Forward” command isdisplayed when the touch gesture is performed on the “F” key, a “Send”command icon associated with the “Send” is displayed when the touchgesture is performed on the “S” key (or possibly “Enter” key), a “NextMessage” command icon associated with the “Next Message” is displayedwhen the touch gesture is performed on the “N” key, a “Previous Message”command icon associated with a “Previous Message” command is displayedwhen the touch gesture is performed on the “P” key, “Delete” commandicon associated with the “Delete” command is displayed when the touchgesture is performed on the “Backspace” key.

In a navigating or browsing context, in some examples, the “N” key maybe associated with a “Next Page” command for displaying a next page ofcontent, “P” key may be associated with a “Previous Page” command fordisplaying a previous page of content, the “T” key may be associatedwith a “Top” command which displays a top portion of a currentlydisplayed item (e.g., web page, document, list, electronic messageetc.), the “B” key may be associated with a “Bottom” command whichdisplays a bottom portion of the currently displayed item, or anycombination thereof. Accordingly, a “Next Page” command icon associatedwith the “Next page command is displayed when the touch gesture isperformed on the “N” key, a “Previous Page” command icon associated withthe “Previous Page” command is displayed when the touch gesture isperformed on the “P” key, a “Top” command icon associated with the “Top”command is displayed when the touch gesture is performed on the “T” key,and a “Bottom” command icon associated with the “Bottom” command isdisplayed when the touch gesture is performed on the “B” key.

Other keys may be associated with a command (a so-called key-commandassignment), and may have a peek gesture associated with it in a similarmanner to the example commands described above. The commands associatedwith the keys may be context dependent, for example, depending on anactive mode or open application.

The virtual keyboard 2120 is typically displayed or invokedautomatically in response to the display or selection of a text entryfield. In some examples, the virtual keyboard 2120 may be toggledbetween a hidden state and a shown state in response to respective inputsuch as, but not limited to, an onscreen virtual keyboard toggle button.In some examples, the virtual keyboard 2120 may be displayed or invokedout-of-context when no text entry field is present to permit the peekgestures and associated shortcuts for executing commands to be used. Theassociated shortcuts may be faster and more intuitive for some userscompared with navigating a menu or other graphical user interfaceelement to select the appropriate command. For example, users familiarwith shortcuts on a device with a physical keyboard may be familiar withcertain key-command associations and may be able to execute commandsmore quickly using the key-command associations via the virtual keyboard2120, even if the virtual keyboard 2120 has to be invoked to access thekeys and activate the shortcut commands. Advantageously, this solutioncan be used to leverage shortcuts conventionally used in devices havingphysical keyboards in a virtual way.

The visual cues described above are believed to have potentialadvantages in several respects which provide a more natural interactionwith the device. Offsetting visual cues based on the input direction ofthe touch input, reduces or eliminates obscuring of the visual cue by aninput implement (e.g., finger or stylus) and facilities interaction withthe visual cue (e.g., tooltip). Moreover, in some instances, thevisibility of the touch input feedback to the user may be improved.Providing more natural interaction with the device involves identifyingefficient interactions (such as gestures) which are relatively easy toperform, relatively easy to remember, have discoverability which allowsusers to “discover” functions during normal use without formal training,and which can be differentiated from other interactions (such asgestures) by users (and by the device) relatively easily. Arbitrary orpoorly considered interaction-action assignments (e.g., gesture-actionassignments) tend to create awkward and unnatural user experiences whichmake the required interaction harder to perform, harder to remember,undiscoverable (or at least less discoverable), and harder todifferentiate from other interactions by users.

Unlike a conventional physical keyboard, a virtual keyboard presents anopportunity for shortcuts, hot keys or other commands to be discoveredby the user. This allows users to “discover” functions during normal usewithout formal training. The specific interaction-action assignmentsdescribed herein are also believed to be relatively easy to perform,relatively easy to remember, have good discoverability, and which can bedifferentiated from other interactions by users (and by the device)relatively easily.

FIG. 31 is a flowchart of a method 3100 for input using a virtualkeyboard rendered on a display of an electronic device 100 in accordancewith one example embodiment of the present disclosure. The virtualkeyboard has at least two input states but could have more than twoinput inputs. The method 3100 may be carried out, at least in part, byfirmware or software executed by the processor 102. Coding of softwarefor carrying out such a method 3100 is within the scope of a person ofordinary skill in the art provided the present disclosure. The method3100 may contain additional or fewer processes than shown and/ordescribed, and may be performed in a different order. Computer-readablecode executable by the processor 102 to perform the method 3100 may bestored in a computer-readable medium such as the memory 110.

At 3120, a virtual keyboard is rendered and displayed on thetouch-sensitive display 118. The virtual keyboard may be displayedautomatically when an input field is displayed or may be called orinvoked, for example, in response to corresponding input (such asactivation of a keyboard button or icon). The virtual keyboard includesa plurality of keys including a plurality of character keys aspreviously described. Each key in the plurality of character keyscorresponds to a character in an input character set. The inputcharacter set, in at least some examples, is an English alphanumericcharacter set. The plurality of character keys are arranged in afamiliar QWERTY layout in the shown example but may be arranged inanother suitable format in other examples. The virtual keyboard may bearranged in the same or similar configuration to those described above.

At block 3130, a touch input is detected on the touchscreen 118 at alocation associated with a key.

At block 3140, the electronic device 100 determines a type of touchgesture of the detected touch input. In some examples, the electronicdevice 100 determines whether the touch input is a first type of gestureinput or a second type of gesture. In some examples, the first type ofgesture is a tap on or near the key and the second type of gesture is aswipe in a particular direction (e.g., down swipe) which has an initialcontact point on or near the key.

At block 3150, when the touch input is a first type of gesture, a firstinput associated with the key is input. When the key is a character key,the first input is character input which corresponds to a characterdisplayed in the key in the virtual keyboard. For example, tapping acharacter key inputs a character from an input character set associatedwith the key. The first input may be a command when the key is anon-character key (e.g., function key).

At optional block 3145, the electronic device 100 may perform an actionif the touch input does not correspond to either the first touch gestureor second touch gesture but does correspond to other designated input(such as a third touch gesture). The action could be input of analternative character or execution of an alternative command differentthan that associated with the first touch gesture and second touchgesture for the particular key.

At block 3160, when the touch input is a second type of gesture and acommand is associated with the key and the second type of gesture, thecommand associated with the key is executed by the electronic device 100is executed by the electronic device 100. Unlike the previouslydescribed example in FIG. 29, no visual cue of the command is provided.

In a messaging context, in some examples, the “R” key may be associatedwith the “Reply” command, the “L” key may be associated with the “ReplyAll” command, the “F” key may be associated the “Forward” command, the“S” key may be associated the “Send” command to send an open messageunder composition, the “N” key may be associated with the “Next Message”commands the “N”, the “P” key may be associated with the “PreviousMessage” command, or any combination thereof. Alternatively, the “Send”command may be associated with the “Enter” key. In a text entry mode,which may be in a messaging context, the “Backspace” key may beassociated with the “Delete” command.

In a navigating or browsing context, in some examples, the “N” key maybe associated with the “Next Page”, the “P” key may be associated withthe “Previous Page” commands, the “T” key may be associated with the“Top” command, the “B” key may be associated with the “Bottom” command,or any combination thereof.

Other keys may be associated with a command (a so-called key-commandassignment) in a similar manner to the example commands described above.The commands associated with the keys may be context dependent, forexample, depending on an active mode or open application.

While the various methods of the present disclosure have been describedin terms of functions shown as separate blocks in the Figures, thefunctions of the various blocks may be combined during processing on anelectronic device. Furthermore, some of the functional blocks in theFigures may be separated into one or more sub steps during processing onan electronic device.

While the present disclosure is described, at least in part, in terms ofmethods, a person of ordinary skill in the art will understand that thepresent disclosure is also directed to the various components forperforming at least some of the aspects and features of the describedmethods, be it by way of hardware components, software or anycombination of the two, or in any other manner. Moreover, the presentdisclosure is also directed to a pre-recorded storage device or othersimilar computer readable medium including program instructions storedthereon for performing the methods described herein.

The present disclosure may be embodied in other specific forms withoutdeparting from the subject matter of the claims. The described exampleembodiments are to be considered in all respects as being onlyillustrative and not restrictive. The present disclosure intends tocover and embrace all suitable changes in technology. The scope of thepresent disclosure is, therefore, described by the appended claimsrather than by the foregoing description. All changes that come withinthe meaning and range of equivalency of the claims are intended to beembraced within their scope.

1-17. (canceled)
 18. A method for providing visual cues rendered on adisplay, comprising: detecting a touch input associated with a userinterface element rendered on the display; determining whether the touchinput is associated with a left hand or a right hand of a user; anddisplaying on the display a visual cue associated with the userinterface element, wherein the visual cue is located at a position basedon whether the touch input is associated with the left hand or the righthand.
 19. The method of claim 18, wherein the visual cue is located tothe right of the user interface element when the touch input isassociated with the left hand of the user, and the visual cue is locatedto the left of the user interface element when the touch input isassociated with the right hand of the user.
 20. The method of claim 18,wherein the user interface element is a key of a virtual keyboardrendered on the display. 21-22. (canceled)
 23. The method of claim 18,wherein determining whether the touch input is associated with the lefthand or the right hand of the user is based on whether the touch inputis detected on a left portion or a right portion of a virtual keyboardrendered on the display.
 24. The method of claim 18, wherein detectingthe touch input comprises determining a shape of the touch input. 25.The method of claim 24, wherein determining whether the touch input isassociated with the left hand or the right hand of the user comprisescomparing the shape of the touch input to a plurality of touch profilesto determine a matching touch profile, and determining the left hand orthe right hand association as a left hand or a right hand association ofthe touch profile which matches the shape of the touch input.
 26. Themethod of claim 25, wherein the plurality of touch profiles include atleast one of a plurality of common shapes for left finger touches, aplurality of common shapes for right finger touches, a plurality ofcommon shapes of stylus touches held by a left hand, or a plurality ofcommon shapes of stylus touches held by a right hand.
 27. Anon-transitory computer readable medium for providing visual cuesrendered on a display of an electronic device, the computer readablemedium comprising instructions which, upon execution by a processor ofthe electronic device, cause the electronic device to: detect a touchinput associated with a user interface element rendered on the display;determine whether the touch input is associated with a left hand or aright hand of a user; and display on the display a visual cue associatedwith the user interface element, wherein the visual cue is located at aposition based on whether the touch input is associated with the lefthand or the right hand.
 28. The non-transitory computer readable mediumof claim 27, wherein the visual cue is located to the right of the userinterface element when the touch input is associated with the left handof the user, and the visual cue is located to the left of the userinterface element when the touch input is associated with the right handof the user.
 29. The non-transitory computer readable medium of claim27, wherein the user interface element is a key of a virtual keyboardrendered on the display.
 30. The non-transitory computer readable mediumof claim 27, wherein determining whether the touch input is associatedwith the left hand or the right hand of the user is based on whether thetouch input is detected on a left portion or a right portion of avirtual keyboard rendered on the display.
 31. The non-transitorycomputer readable medium of claim 27, wherein detecting the touch inputcomprises determining a shape of the touch input.
 32. The non-transitorycomputer readable medium of claim 31, wherein determining whether thetouch input is associated with the left hand or the right hand of theuser comprises comparing the shape of the touch input to a plurality oftouch profiles to determine a matching touch profile, and determiningthe left hand or the right hand association as a left hand or a righthand association of the touch profile which matches the shape of thetouch input.
 33. The non-transitory computer readable medium of claim32, wherein the plurality of touch profiles include at least one of aplurality of common shapes for left finger touches, a plurality ofcommon shapes for right finger touches, a plurality of common shapes ofstylus touches held by a left hand, or a plurality of common shapes ofstylus touches held by a right hand.
 34. An electronic device,comprising: a touch-sensitive display; and one or more processorsconfigured to: detect a touch input associated with a user interfaceelement rendered on the display; determine whether the touch input isassociated with a left hand or a right hand of a user; and display onthe display a visual cue associated with the user interface element,wherein the visual cue is located at a position based on whether thetouch input is associated with the left hand or the right hand.
 35. Theelectronic device of claim 34, wherein the visual cue is located to theright of the user interface element when the touch input is associatedwith the left hand of the user, and the visual cue is located to theleft of the user interface element when the touch input is associatedwith the right hand of the user.
 36. The electronic device of claim 34,wherein the user interface element is a key of a virtual keyboardrendered on the display.
 37. The electronic device of claim 34, whereindetermining whether the touch input is associated with the left hand orthe right hand of the user is based on whether the touch input isdetected on a left portion or a right portion of a virtual keyboardrendered on the display.
 38. The electronic device of claim 34, whereindetecting the touch input comprises determining a shape of the touchinput.
 39. The electronic device of claim 38, wherein determiningwhether the touch input is associated with the left hand or the righthand of the user comprises comparing the shape of the touch input to aplurality of touch profiles to determine a matching touch profile, anddetermining the left hand or the right hand association as a left handor a right hand association of the touch profile which matches the shapeof the touch input.